Mobile application for providing multiple second line numbers on single mobile device

ABSTRACT

A mobile application and a method are described for servicing a second line service (“SLS”) based communication request originating from a subscriber&#39;s telecommunications device (“TD”) even if the call signal does not include sufficient information to identify the phone number from which the subscriber initiated the call. The method involves associating the SLS phone number of the subscriber, the primary number of the subscriber and the primary number of a third party via a special relationship number.

BACKGROUND

When a second line service (“SLS”) provider offers a method for routingcalls between an SLS subscriber's telecommunications device (“TD”) and athird party's TD, the method may involve using a common relationshipnumber associated to (1) the SLS number of the SLS subscriber, (2) theprimary phone number (or any phone number from which the SLS subscribercan make/receive a call) and (3) the primary phone number of a thirdparty (or any phone number from which the SLS subscriber canmake/receive a call). In the typical SLS scenario, an SLS based call orcommunication is initiated from the TD of an SLS subscriber, anddirected toward a particular third party or other final destination bythe SLS subscriber entering or selecting the relationship number,directly or indirectly. These SLS based call or communications arerouted to an SLS platform or server and then redirected by the SLSplatform or server to a third party TD that is identified or associatedwith the relationship number. More specifically, the SLS leverages therelationship number such that the SLS call is routed to the SLS platformor server. At the SLS platform or server, the combination of the phonenumber associated with the subscriber TD used to initiate the SLS basedcall, and the relationship number identified in the SLS call, allows theSLS platform or server to identify the third party or the ultimatedestination number. The SLS platform is then able to route the SLS basedcall to the third party number for call completion.

Unfortunately, it is not always possible for an SLS platform todetermine the phone number associated with the subscriber TD used toinitiate the SLS based call. In certain circumstances the call signalchanneled through the telecommunications network handling the call orcommunication may not include sufficient information, such as thecalling line identification (“CLID”) or any other data necessary toidentify the phone number associated with the TD initiating the SLSbased call. This missing CLID data may be the result of thetelecommunication network, or its associated elements, not making theinformation available, not making the information reliably available,not making the information consistently available, etc. For example,when an SLS subscriber is roaming to a telecommunications networkdifferent from its primary, or “home,” telecommunications network, theCLID may not be available.

Regardless of what causes the CLID to be missing, the SLS platform orserver cannot identify the third party or destination number at which toterminate the SLS based call if it does not have the subscriber TD'sCLID. Accordingly, what is needed is a system and method for providingan SLS to a subscriber TD when the subscriber TD's CLID is missing.

SUMMARY OF THE DISCLOSURE

A method and system are described for servicing an SLS basedcommunication request originating from a subscriber's TD even if thecall signal does not include sufficient information to identify thephone number from which the subscriber initiated the request. Suchembodiments will be referred to as CLID agnostic SLS systems.

In general, the operation of various embodiments that are CLID based arefirst described to provide an overall understanding of the SLS.Following this, the operation of various embodiments that are CLIDagnostic is presented. The embodiments in the CLD based system mayoperate in an environment in which an SLS platform is interposed betweena network serving as the primary service provider to a subscriber's TDand a network serving as the primary service provider to a third partyTD. As such, a call originating from a third party TD and directedtowards the SLS number associated with the TD of an SLS subscriber, isrouted by the receiving network to an SLS platform or server forprocessing.

Upon receiving the call, the SLS platform queries a local database toidentify a relationship number that serves to map the primary number ofthe subscriber's TD to the combination of the third party calling numberand the subscriber's second line number. The call is then redirected tothe primary number of the subscriber's TD along with or in addition to,information that identifies the call as being directed to the SLSnumber. Once received by the subscriber's TD, the call setup iscompleted. Additional information may be included within the call signalsuch that an application running, associated with or resident on thesubscriber's TD can save the combination in a local database on thesubscriber's TD.

Advantageously, the relationship number so delivered to the subscriber'sTD can be used at a later time to initiate an SLS based call to a thirdparty. As a non-limiting example, dialing the third party's telephonenumber or otherwise initiating a call to the third party from the SLSapplication on the subscriber's TD can result in dialing or initiating acall to the relationship number for the third party. As such, when thecall enters the telephone network (such as the PSTN, MTSO, etc.) thecall is actually routed to the SLS platform. The SLS platform may thenuse the relationship number to identify the actual destination number ofthe third party and the SLS number that is attributed to being theoriginator of the call. Next, the SLS platform routes, bridges,transfers, initiates or otherwise establishes a completed communicationpath, or the delivery of a message from the originating TD to thedestination TD. As a non-limiting example, using the actual third partycalled number, the SLS platform may complete the second leg of the call.In certain embodiments, a call leg between a subscriber's TD and the SLSplatform may be completed using a session initiated protocol (“SIP”) sothat the data service provided by the primary service provider of thesubscriber device is used in lieu of a voice channel.

However, if a subscriber TD attempts to direct an SLS based call to athird party number the does not have an associated relationship number,the call may be directed to, or invoke the routing of the call to theSLS platform by placing the call to a new relationship number selectedby an SLS client application running on the subscriber's TD. In suchcase, the relationship number invokes the telecommunications network toroute the call to the SLS platform and the third party number isprovided to the SLS platform from the subscriber's TD. In otherembodiments, the new relationship number may be requested from the SLSplatform before making the call and then used by the subscriber's TD tomake the call. In either case, a new relationship number is used todirect the call from the subscriber's TD toward the third partydestination and to trigger the telecommunications network to route thecall to the SLS platform.

In the databases located at or accessible to the subscriber's TD and theSLS platform, the new relationship number maps the subscriber's primarynumber to the combination of the third party number and the subscriber'ssecond line number. The call is redirected by the SLS platform to thenumber associated with the third party TD and the call is completed.Advantageously, the new relationship number can be used at a later timeshould the subscriber desire to call the third party as previouslydescribed.

By associating the SLS phone number of the subscriber, the primarynumber of the subscriber and the phone number of a third party via acommon relationship number, SLS based calls can be directed to and froman SLS of a subscriber TD.

Understanding the general operation of the SLS, the specific CLIDagnostic embodiments can now be better understood. In general, thisaspect of the various embodiments utilizes a different type ofrelationship number than has been previously presented. The “Normal”relationship numbers, as presented above, may exist in a common poolused by multiple SLS subscribers. The translation of the specificinformation, e.g. which SLS phone number is calling and to which thirdparty telephone number the second leg of the SLS should be directed, bythe SLS platform requires two pieces of information from the callsignal: the actual primary number associated with the subscriber TD andthe relationship number.

Thus, a problem arises when the call signal from the subscriber's TDdoes not include sufficient information, such as CLID or any other datanecessary to identify the phone number associated with the subscriberTD. For example, this problem may arise when a subscriber TD roams to avisited network where proper identification of the calling number is notavailable or not reliably or consistently included in the signaling. Ifthe primary number is not properly transmitted in the signaling, thelook-up based on the relationship number and originating numberobviously cannot be performed.

In addressing this issue, the various CLID agnostic embodiments operateto create a pool of additional “special” relationship numbers. Thesespecial relationship numbers are used for one specific subscriber TD ata time. Through negotiation between the subscriber's TD and the SLSplatform or server, the server will assign a special relationship numberto that specific subscriber TD. These special relationship numbers canbe used for multiple purposes, with the specific meaning established aspart of the client-server negotiation.

The duration of the assignment of that special relationship number to aspecific subscriber TD can be based on an event occurring, e.g. a callis placed, based on a timer, or durable until explicitly cancelled bythe subscriber TD or by the SLS platform.

Because the special relationship number is assigned by the server to aknown, specific subscriber TD, the SLS platform does not need the CLID,or any other data useful for identification of the phone number beingused by and associated with subscriber TD. Instead, the SLS platform hasassigned the specific special relationship number to that particular SLSsubscriber and, furthermore, it can determine the third party to whichthe SLS based call is intended.

In some embodiments, the SLS platform may communicate with thesubscriber TD that a special relationship number is needed because thesubscriber is in a CLID agnostic sytem. Additionally, it is envisionedby this disclosure that the SLS platform may assign a specialrelationship number or request a special relationship number from theSLS platform for the third party phone number upon the occurrence of aquery error for “Normal” relationship number methods and systems, upon aspecific request by the SLS subscriber (either directly to the SLSprovider, indirectly to the SLS provider using the SLS application,etc.), upon a specific triggering event, e.g., the roaming of thesubscriber TD to a foreign communications network, etc.

In certain embodiments, regardless of how, when or for how long thespecial relationship number is assigned, the subscriber TD mayeventually receive a communication from the SLS platform with thespecial relationship number assignment information. The SLS platform maythen store the combination of the special relationship number and thethird party phone number in the local SLS database.

In certain embodiments involving a query error, despite SLS platform'squery error, the subscriber TD can establish a communication with theSLS platform using the special relationship number associated with thedialed third party number. The subscriber TD phone application may queryits local SLS database and translates the intended third party number toyield the specific special relationship number. Having queried thespecial relationship number, the SLS phone app may place the call to theSLS platform from subscriber's primary phone number to the specialrelationship number.

When the SLS platform determines that this call was received at thespecific special relationship number, it recognizes that the callingparty is the SLS subscriber despite the CLID agnostic circumstances. Asa result, the SLS platform does not need to query a “Normal”relationship number. Instead, the SLS platform queries using thefollowing logic: “a call was received at a specific special relationshipnumber, so this means that the SLS subscriber is wanting to call anassociated third party phone number using its SLS phone number.” The SLSplatform may then follow that logic and complete a second call bycalling the third party number using the SLS number.

BRIEF DESCRIPTION OF THE DRAWINGS

In the figures, like reference numerals refer to like parts throughoutthe various views unless otherwise indicated. For reference numeralswith letter character designations such as “102A” or “102B”, the lettercharacter designations may differentiate two like parts or elementspresent in the same figure. Letter character designations for referencenumerals may be omitted when it is intended that a reference numeralencompass all parts having the same reference numeral in all figures.

FIG. 1 is a high level diagram illustrating exemplary components of asystem for providing an SLS to a subscriber TD 110.

FIG. 2 is a diagram of an exemplary network architecture for the systemof FIG. 1 .

FIGS. 3A-3D are exemplary data tables that may be leveraged by aredirection module of an SLS platform and an SLS module of a subscriberTD to provide a second line service to a user of subscriber TD.

FIGS. 4A-4E collectively illustrate an exemplary method 400 forimplementing an SLS call between a third party TD and a TD associatedwith an SLS subscriber when the call signal from the subscriber TD doesnot include the CLID or any other data useful for identification of thephone number being used by and associated with subscriber TD for thecall.

DETAILED DESCRIPTION

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother aspects.

In this description, the terms “application” and “app” may also includefiles having executable content, such as: object code, scripts, bytecode, markup language files, and patches. In addition, an “application”referred to herein, may also include files that are not executable innature, such as documents that may need to be opened or other data filesthat need to be accessed. Further, an “application” may be a completeprogram, a module, a routine, a library function, a driver, etc.

The term “content” may also include files having executable content,such as: object code, scripts, byte code, markup language files, andpatches. In addition, “content” referred to herein, may also includefiles that are not executable in nature, such as documents that may needto be opened or other data files that need to be accessed.

As used in this description, the terms “component,” “database,”“module,” “system,” and the like are intended to refer to acomputer-related entity, either hardware, firmware, a combination ofhardware and software, software, or software in execution. For example,a component may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on a computing device and the computing device maybe a component.

One or more components may reside within a process and/or thread ofexecution, and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentsmay execute from various computer readable media having various datastructures stored thereon. The components may communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets, e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems by way of the signal).

In this description, the terms “telecommunications device,”“communication device,” “wireless device,” “wireless telephone,”“wireless communication device” and “wireless handset” are usedinterchangeably. With the advent of third generation (“3G”) and fourthgeneration (“4G”) wireless technology, greater bandwidth availabilityhas enabled more portable computing devices with a greater variety ofwireless capabilities. Therefore, a telecommunications device (“TD”) mayinclude a cellular telephone, a pager, a PDA, a smartphone, a navigationdevice, a tablet personal computer (“PC”), or a hand-held computer witha wireless connection or link.

In this description, the terms “call” and “communication,” in their nounforms, envision any data transmission routed across a network from onedevice to another including, but not limited to, a voice transmission, atext message, a video message, a page, a data transmission, etc.

FIG. 1 is a high level diagram illustrating exemplary components of asystem 100 for providing an SLS to a subscriber TD 110. In general, anSLS based call can be originated by a subscriber TD 110 and directedtoward a non-subscriber or subscriber third party TD 120 or beoriginated by a non-subscriber or a subscriber third party TD 120 anddirected towards a subscriber TD 110. The typical subscriber TD 110 isassociated with a primary phone number assigned to it and provisionedand serviced by the subscriber's home mobile service provider (“primaryservice provider”) as is understood by one of ordinary skill in the art.A subscriber to an SLS offered through exemplary system 100 may receivecalls at the subscriber TD 110 that are originally directed to either ofthe primary phone number provided by the primary service provider or thesecondary phone number (“SLS phone number”) provided, serviced and orfacilitated by the SLS platform 115. It will also be appreciated that insome embodiments, the subscriber TD 110 may only include SLS operationand not include a primary number at all. In such embodiments, anycommunication between the TD 110 and the servicing network would occurover a data channel rather than a voice channel. In such embodiments,the TD 110 could actually be a computer device connected to theInternet. Yet in other embodiments, the TD 110 may include a minimalizedprimary number service that is greatly restricted. For instance, minimalmobile service only includes the ability to make a 911 emergency call.In some embodiments, one step above such limitation may be provided tothe TD 110 such that the TD 110 can only operate to exchange sufficientinformation with the network to establish an SLS call.

Notably, depending on the particular embodiment, the primary serviceprovider and the SLS platform, i.e., the second line service provider,may be the same provider or different providers. In embodiments wherethe primary service provider and the second line service provider aredifferent providers, the SLS subscriber may receive separate billingrecords from each provider. However, it is envisioned that certainembodiments where the primary service provider and the second lineservice provider are not one and the same may take advantage of sessioninitiated protocols (“SIP”) to simplify billing records for the user.

In general, any call directed to either of the primary phone number orthe SLS phone number are transmitted from a third party TD 120 to thesubscriber TD 110 by way of communications network 125. Notably,communications network 125 envisions any and all networks fortransmitting and terminating communications between TDs such as, but notlimited to, cellular networks, PSTNs, cable networks and the Internet.Methods for effecting the transmission of data across communicationsnetwork 125 from one device to another, including call setups,terminations and the like are understood by those of ordinary skill inthe art of data transmission and may include the use of protocols andstandards such as, but not limited to, signaling system seven (“SS7”)protocol suite, SIP, customized applications for mobile networksenhanced logic (“CAMEL”) or CAMEL Application Part (“CAP”), remoteoperations service element (“ROSE”), Voice Over IP (“VOIP”), proprietarytechniques, etc. Notably, while the use of any particular protocol orcommunications standard may be a novel aspect of a particular embodimentof the systems and methods, it will be understood that the scope of thesystems and methods disclosed herein is not limited to the use of anyparticular protocol or combination of protocols.

A call made from a third party TD 120 to the primary number associatedwith subscriber TD 110 is transmitted across communications network 125and routed to subscriber TD 110, as is understood in the art. The radiotransceiver 104, if the TD 110 is a portable and wireless device,enables the receipt and transmission of signals to and from subscriberTD 110. The call signal may include the calling line identification(“CLID”), i.e., the phone number being used by and associated with thirdparty TD 120 for the call, such that when the call is received atsubscriber TD 110 the CLID may be displayed for the benefit of the SLSsubscriber on display component 103. It is envisioned by this disclosurethat in certain circumstances the call signal may not include the CLIDor any other data useful for identification of the phone number beingused by and associated with the call-originating TD. It is known bythose of ordinary skill in the art that this missing data may be theresult of communications network 125 (and the associated elements suchas third party TD 120, subscriber TD 110, SLS platform 115 or the like)not making the information available, not making the informationreliably available, not making the information consistently available,etc.

The various embodiments of the SLS system and method described in thepresent disclosure provide the SLS even if the CLID or other identifyinginformation of the subscriber TD 110 is not available at the time ofsetting up a call by the subscriber TD 110. Such a scenario can occurwhen the subscriber, or the TD 110 of the subscriber, is being operatedin a roaming manner. The various embodiments of the CLID agnostic SLSdescribed in the present disclosure are mainly focused on the situationin which a call is originated by a subscriber TD 110.

Notably, although the exemplary embodiments described in the presentdisclosure use the CLID as an example of data that may be displayed forthe benefit of the user of a subscriber TD 110, it will be understoodthat any data associated with the third party TD 120, subscriber TD 110,SLS platform 115 or the like may be rendered for the benefit of the userof the system 100 and, as such, only describing that the CLID isdisplayed will not limit the scope of what is envisioned by thedisclosure. Moreover, it is envisioned that any data uniquely associatedwith a call to a primary number or an SLS phone number may be displayedfor the benefit of a SLS subscriber to the system 100.

Returning to the FIG. 1 illustration, a call made from a third party TD120 to an SLS phone number associated with subscriber TD 110 istransmitted across communications network 125. As one of ordinary skillin the art will understand, the communications network 125 routes thecall based on the dialed SLS phone number and routes the call to SLSplatform 115. This is the first leg of the SLS. The SLS platform 115thus effectively intercepts or receives the call, determines that thecall was intended for subscriber TD 110 and then takes actions such thatthe call can be terminated at the subscriber TD 110. This is the secondleg of the SLS. In this way, while a call directed to a primary numberassociated with subscriber TD 110 is routed directly to subscriber TD110, a call directed to a second line number associated with subscriberTD 110 is routed to the SLS platform 115 instead.

Once the call is received at SLS platform 115, a query of central SLSdatabase 116 by redirection module 117 determines that the call fromthird party TD 120 was meant for the second line number associated withsubscriber TD 110. Once the determination is made, redirection module117 processes the call and performs additional network functions suchthat the call is made available for termination at subscriber TD 110through its SLS.

Because the call may include data identifying it as a call to the SLSphone number (one of multiple possible network functions performed byredirection module 117 and/or other SLS platform 115 components)associated with subscriber TD 110, the SLS module 105 intercepts theincoming call, or otherwise injects itself into the call processingactivity for the call, and then leverages data stored in the local SLSdatabase 106 to render it in such a way that subscriber TD 110 processesor recognizes the call as an SLS call as opposed to a call directed atits primary phone number. For instance, the SLS module 105 is designedto work with radio transceiver 104 and any stored or retrievable contentin local SLS database 106 to terminate a call to an SLS phone number,render associated data and provide services uniquely associated with theSLS phone number such as, but not limited to, dedicated voicemail,ringtones, caller ID, automated responses, etc.

It is envisioned by this disclosure that in certain circumstances, theSLS platform 115 may not be able to determine the identity of the thirdparty TD 120 (for the reasons stated above), and thus, a query ofcentral SLS database 116 by redirection module 117 using the phonenumber associated with third party TD 120 for the call may beimpossible. Nonetheless, under these circumstances, the SLS platform 115has a process for effectively intercepting the call, determining thatthe call was intended for subscriber TD 110, and then taking actionssuch that the call can be terminated at the subscriber TD 110.

A more detailed description of the exemplary method, including exemplarymethods for (1) receiving a call from a third party TD 120, (2) making acall to a third party TD 120 and (3) performing (2) when the call signalfrom the subscriber TD 110 does not include the CLID or any other datauseful for identification of the phone number being used by andassociated with the calling TD, by way of the SLS platform 115 will bedescribed below relative to FIG. 4 .

Referring to FIG. 2 , a diagram of exemplary network architecture 101for the system 100 of FIG. 1 is depicted. The exemplary networkarchitecture 101 may include a subscriber TD 110 and a third party TD120. Notably, although the third party TD 120 is not illustrated tosuggest that it is equipped with SLS capability, it is envisioned thatin some embodiments both the subscriber TD 110 and the third party TD120 may be SLS enabled.

As illustrated in FIG. 2 , an SLS platform 115 may be connected to thesubscriber TD 110 via a first provider network 201 and to the thirdparty TD 120 via a second provider network 202, although it isenvisioned that TDs 110 and 120 may be associated with a common serviceprovider in some embodiments. One of ordinary skill in the art wouldrecognize that communications network 125 from FIG. 1 can be comprisedof smaller networks like first provider network 201 and second providernetwork 202.

It is envisioned that the first provider network 201 and the secondprovider network 202 can be the same network. Additionally, it isenvisioned that the first provider network 201 and the second providernetwork can be operated, serviced, owned, etc. by the same or differentservice provider(s), and it is envisioned that either, or both, serviceproviders respectively associated with provider networks 201 or 202 mayfunction as both a primary service provider and/or an SLS provider for agiven subscriber TD 110 or third party TD 120. Furthermore, it isenvisioned that either or both of subscriber TD 110 and third party TD120 may be associated with a primary service provider and a separate SLSprovider.

Notably, depending on the particular embodiment, first provider network201 or second provider network 202 may not make the CLID, or other datauseful for identification of the phone number being used by andassociated with the calling TD, available, may not make the informationreliably available, may not make the information consistently available,etc.

For exemplary purposes, the subscriber TD 110 is depicted as being SLSenabled and the third party TD 120 is depicted as not having a secondline service associated with it. Moreover, first provider network 201and the second provider network 202 are the same network in FIG. 2 .Finally, first provider network 201 and the second provider network 202are depicted as networks that, at certain times and under certaincircumstances, may not make the CLID, or other data useful foridentification of the phone number being used by and associated with thecalling TD, available, reliably available, consistently available, etc.Despite what is depicted for exemplary purposes, other combinations ofprimary and secondary service provider networks connecting SLS platform115 to subscriber TD 110 and third party TD 120 are envisioned.

In FIG. 2 , it can be seen that the SLS platform 115 may include an SLSserver 205 configured to receive calls directed to and from an SLS phonenumber associated with subscriber TD 110. The SLS server 205 includes aprocessor 209 and a memory 211 coupled to the processor 209. For someembodiments, the memory 211 may include instructions for executing oneor more of the method steps described herein. Further, the processor 209and the memory 211 may serve as a means for executing one or more of themethod steps described herein. As indicated, the memory 211 may alsoinclude a redirection module 117 and a central SLS database 116.Notably, it should be understood that the term server 205 may refer to asingle server system or multiple systems or multiple servers. One ofordinary skill in the art will appreciate that the various serverarrangements may be selected depending upon computer architecture designconstraints without departing from the scope of the invention.

As further illustrated in FIG. 2 , the subscriber TD 110 may include aprocessor 208 and a memory 207 coupled to the processor 208. For someembodiments, the memory 207 may include instructions for executing oneor more of the method steps described herein. Further, the processor 208and the memory 207 may serve as a means for executing one or more of themethod steps described herein. As indicated, the memory 207 may alsoinclude an SLS module 105 and a local SLS database 106.

Illustrative embodiments for providing an SLS to an SLS subscriber aredescribed in the context of the system and network architecturedescribed in FIGS. 1-2 and the exemplary data tables reflected in FIGS.3A-3D. Specifically, three different embodiments are described: oneembodiment describes receiving a call through an SLS from a third partyTD 120 when the call signal includes the CLID or any other data usefulfor identification of the phone number being used by and associated withthe calling TD; the second embodiment describes making a call through anSLS to a third party TD 120 when the call signal includes the CLID orany other data useful for identification of the phone number being usedby and associated with the calling TD; the third embodiment describesthe second embodiment when the call signal does not include the CLID orany other data useful for identification of the phone number being usedby and associated with the calling TD.

As previously stated, FIG. 1 illustrates a call made from a third partyTD 120 to an SLS phone number associated with subscriber TD 110. As oneof ordinary skill in the art will recall, the communications network 125routes the call based on the called number (the SLS phone numberassociated with the SLS subscriber). Ultimately, communications network125 routes the call to SLS platform 115. SLS platform 115 effectivelyintercepts the call, determines that the call was intended forsubscriber TD 110 and then takes actions using “relationship numbers”such that the call can be terminated at the subscriber TD 110.Consequently, all the illustrative embodiments of the method involveleveraging two sets of intermediate phone numbers, one set ofintermediate phone numbers for one leg of the SLS and the other for thesecond leg of the SLS, such that calls directed to subscriber TD 110ultimately terminate at TD 110 using the SLS.

FIGS. 3A-3D are exemplary data tables that may be leveraged by aredirection module 117 of an SLS platform 115 and an SLS module 105 of asubscriber TD 110 to provide a second line service to a user ofsubscriber TD 110. The Second Line Service Master ID Table 305 andSubscriber Relationship ID Table 310 of FIG. 3A are stored in a centralSLS database 116 while the exemplary Subscriber Relationship ID Table315 of FIG. 3B are stored in a local SLS database 106 of a subscriber TD110. Likewise, the Second Line Service Master ID Table 305 andSubscriber Special Relationship ID Table 320 of FIG. 3C are stored in acentral SLS database 116 while the exemplary Subscriber SpecialRelationship ID Table 325 of FIG. 3D are stored in a local SLS database106 of a subscriber TD 110. As such, some illustrative embodimentsinvolve leveraging two sets of intermediate phone numbers, the phonenumbers related to the Second Line Service Master ID Table 305 and thephone numbers related to the Subscriber Relationship ID Tables. Otherillustrative embodiments involve leveraging two sets of intermediatephone numbers, the phone numbers related to the Second Line ServiceMaster ID Table 305 and the phone numbers related to the SubscriberSpecial Relationship ID Tables. Notably, it is envisioned that in someillustrative embodiments three sets of intermediate phone numbers may beinvolved even though only two sets of intermediate phone numbers areactually leveraged for the first and second leg of the SLS.

With regard to the first embodiment and to the leveraging of the firstset of intermediate phone numbers, specifically the phone numbersrelated to the Second Line Service Master ID Table 305, once the callreaches the SLS platform 115, an application running on redirectionmodule 117 makes a translation to complete this first leg of the SLS.The SLS platform 115 maintains a master list of SLS phone numbers thatare in service. In some embodiments, the SLS provider may be the owner,lessee, or assignee, etc. of these SLS phone numbers.

In the communications network 125, these SLS phone numbers route to theSLS platform 115, i.e., the SLS platform may be communicatively coupledwith communications network 125, and any of its component networks likefirst provider network 201 or second provider network 202, such that acall directed at the SLS phone number is ultimately routed to the SLSplatform. However, one of ordinary skill in the art will recognize that,depending on which provider network the SLS phone number is associated,a call directed at/directed from the SLS phone number is usually routedthrough its associated provider network before terminating at the SLSplatform. For example, in FIG. 2 , if the SLS phone number is associatedwith first provider network 201, then any call direct at/directed fromthe SLS phone number is routed through first provider network 201regardless of the SLS phone number being owned, lease, or assigned, etc.by a separate SLS provider.

The SLS provider that manages the SLS platform 115 essentially has agroup of SLS phone numbers in inventory, and the SLS provider assignsthe SLS phone numbers to subscribers of the SLS. Regarding the SLSprovider's inventory of SLS phone numbers, one of ordinary skill in theart will recognize that the SLS phone numbers may be random andgenerally unrelated to each other, i.e., although the exemplary SLSphone numbers depicted in the FIG. 3A Second Line Service Master IDTable are sequential, it is envisioned that such is not the case in allembodiments.

Moreover, one of ordinary skill in the art will recognize that, althoughthe exemplary SLS phone numbers depicted in the FIG. 3A Second LineService Master ID Table 305 include a specific country code, area code,and seven digit directory number, it is envisioned that any countrycode, area code and directory number system known to those skilled inthe art is included within the scope of this disclosure. Additionally,it is envisioned that the SLS provider can maintain a large and diverseinventory of SLS phone numbers; each being associated with itsrespective provider network and, consequently, each routing through itsassociated provider network before terminating at the SLS platform 115.

Referring back to FIGS. 3A-3B and the Second Line Service Master IDTable 305, the example Subscriber #1 has been issued SLS phone number1.770.555.0001. Other SLS subscribers in different situations and withdifferent circumstances are within the scope of this disclosure.Subscriber #1 may choose to give out its SLS phone number to any of itscontacts.

With regard to the first embodiment and to the leveraging of the secondset of intermediate phone numbers, specifically the phone numbersrelated to the Subscriber Relationship ID Tables, for each SLSsubscriber a Subscriber Relationship ID Table 310 is also maintained.Referring to the Subscriber Relationship ID Table 310, the SLS providerhas another list of dialable phone numbers, i.e., relationship numbers,which are maintained. These relationship numbers are essentially “hiddennumbers” that are used to make the second leg of the call between thesubscriber TD 110 and the SLS platform 115.

In some embodiments, the SLS provider may be the owner, lessee, orassignee, etc. of these relationship numbers. Like the SLS phonenumbers, one of ordinary skill in the art will recognize that, dependingon which provider network the relationship numbers are associated, acall directed at/directed from the relationship numbers are usually alsorouted through their associated provider network. For example, in FIG. 2, if the relationship numbers are associated with first provider network201/second provider network 202, then any call directed at/directed fromthe relationship numbers is routed through first provider network201/second provider network 202 regardless of the relationship numberbeing owned, leased, or assigned, etc., by an SLS provider.

Concerning the Subscriber Relationship ID Table 310, one of ordinaryskill in the art will understand that certain embodiments may notformally distinguish one SLS subscriber's records from that of anothervia individual subscriber relationship ID tables. Rather, as isunderstood in the art of database management and query, a more generalrelational database including records associated with multiple SLSsubscribers may be used to map SLS subscriber number and third partynumber combinations to given relationship numbers. As such, it will beunderstood by one of ordinary skill in the art that the description inthis disclosure of exemplary embodiments that include individualsubscriber relationship ID tables are offered for illustrative purposesonly and will not limit the scope of the disclosure.

Additionally, concerning the use of relationship numbers, it isenvisioned that certain relationship numbers may be used for a pluralityof SLS phone numbers and third party number combinations, i.e., incertain embodiments a given relationship number may not be unique to agiven subscriber phone number and third party phone number combination.For example, in an illustrative embodiment, SLS subscribers D, E, F andG, may all have database records that map relationship number X to thirdparty numbers J, K, L and E, respectively. Notably, in this exemplaryscenario, the subscriber phone number and third party number combinationG:E is meant to envision a case where G has a calling relationship withE. In such case, although E is a subscriber to the SLS it may also betreated as a third party caller relative to SLS subscriber G. To carrythe example further, if G has a relationship with E, E also has one withG. However, the E:G combination may or may not use a differentrelationship number, such as Y.

Additionally, it is envisioned that in certain embodiments arelationship number may be used for purposes other than to map a thirdparty calling number in Subscriber Relationship ID Table 310. Forexample, a given relationship number may be used by the SLS platform 115to alert the SLS Module 105 that a call has been received from anunknown caller with a blocked CLID. Or, as another non-limiting example,a given relationship may be used by the SLS platform 115 to alert theSLS Module 105 that a voice message has been deposited for the SLSsubscriber.

Like the SLS phone numbers, the SLS provider essentially has a group ofrelationship numbers in inventory, and the SLS provider assigns therelationship numbers as described above, and as described in greaterdetail below. Regarding the SLS provider's inventory of relationshipnumbers, one of ordinary skill in the art will recognize that therelationship numbers may be random and generally unrelated to eachother, i.e., although the exemplary relationship numbers depicted in theFIG. 3A-3B Subscriber Relationship ID Tables are sequential, it isenvisioned that such is not the case in all embodiments.

Moreover, one of ordinary skill in the art will recognize that, althoughthe exemplary relationship numbers depicted in the FIG. 3A-3B SubscriberRelationship ID Tables include a specific country code, area code, andseven digit directory number, it is envisioned that any country code,area code and directory number system known to those skilled in the artis included within the scope of this disclosure. Additionally, it isenvisioned that the SLS provider can maintain a large and diverseinventory of relationship numbers; each being associated with itsrespective provider network and, consequently, each routing through itsassociated provider network when leveraged by the SLS.

Referring again to FIGS. 3A-3B and the Subscriber Relationship IDTables, the example third parties with numbers 1.305.229.9999,1.212.777.8888 and 1.408.333.2222 have been issued relationship numbers1.678.222.0001, 1.678.222.0002 and 1.678.222.0003 respectively. Otherthird parties in different situations and with different circumstancesare within the scope of this disclosure.

As mentioned above, the relationship numbers are “behind the scenes”numbers that may be hidden from the SLS subscriber and any third partycalling the SLS subscriber through the SLS. This is accomplished by anapp running on SLS module 105 residing on subscriber TD 110. In thisfirst illustrative embodiment, the SLS platform 115 has effectivelyintercepted the first leg of the SLS and determined that the call wasintended for subscriber TD 110 (this was described above). As will bedescribed in greater detail below, SLS platform 115 takes an action thatinvolves the relationship number such that the call can be terminated atthe subscriber TD 110. Essentially, by leveraging the relationshipnumber, an SLS provider may insert itself into the middle of a callbetween a third party TD 120 and a subscriber TD 110.

Returning to the FIGS. 3A-3B and the first illustrative embodiment,Subscriber #1 associated with subscriber TD 110 already has mobile phoneservice via its primary service provider using mobile phone number1.408.544.1212. Subscriber #1 subscribes to an SLS provided by way ofSLS platform 115 and is assigned SLS phone number 1.770.555.0001. Athird party, identified in Subscriber Relationship ID Table 310 of FIG.3A as being Subscriber Contact #1, is associated with a third party TD120A having a primary phone number 1.305.229.9999. Notably, although theprimary phone number 1.305.229.9999 associated with third party TD 120is described herein as a primary phone number, it will be understoodthat it may, in fact, be a second line number in embodiments where thethird party is also an SLS subscriber.

The third party uses TD 120 to place a call to the Subscriber #1's SLSphone number 1.770.555.0001. As described above, the call is routed tothe SLS platform 115. The SLS platform 115 accepts the call anddetermines that the call is for SLS phone number 1.770.555.0001 and that1.770.555.0001 requires a “relationship” set up for 1.305.229.9999. Forpurposes of these exemplary embodiments, Subscriber #1 has only recentlysubscribed to the SLS and Subscriber Relationship ID Table 310 does notyet contain any records, i.e., the third party associated with TD 120 isthe first to place a call to the SLS phone number of Subscriber #1.

The SLS platform 115 creates the following relationship in SubscriberRelationship ID Table 310: When 1.770.555.0001 receives (or places) acall from/to 1.305.229.9999, the interaction with the subscriber TD 110(having primary phone number 1.408.544.1212) will use dialablerelationship number 1.678.222.0001. This relationship number wasselected because it is a relationship number available in inventory tothe SLS subscriber and the third party. Notably, it is envisioned that agiven relationship number, such as relationship number 1.678.222.0001 inthe present example, may be used as a relationship number for manydifferent SLS subscribers as it is the combination of the SLSsubscriber's primary number and/or the SLS phone number and therelationship number that map to the external number (in this case,1.305.229.2999).

Now that the relationship number 1.678.222.0001 has been established inconnection with Subscriber #1 and the calling third party, the SLSplatform 115 may proceed to establish the second leg of the SLS—the callfrom the SLS platform 115 to the subscribers TD 110. The SLS platform115 places the call to the subscriber TD 110. It is known to those withordinary skill in the art that methods for establishing this second legof the SLS include the use of protocols and standards such as, but notlimited to, SS7 protocol suite, SIP, CAMEL or CAP, ROSE, VOIP, etc. Itis of course possible for the SLS platform 115 to direct the call to theprimary number 1.408.544.1212 of the subscriber TD 110 using standardvoice channels.

Returning to the first illustrative embodiment, the CLID field for thecall placed from SLS platform 115 to subscriber TD 110 may contain aspecially encoded message for the SLS phone app running on SLS module105. In some embodiments, this CLID field may contain the relationshipnumber established by the SLS platform 115 (in this example,1.678.222.0001) and the actual primary number of the calling third party(in this example, 1.305.229.9999), separated by a dialable separatorsuch as a “star” character. In other embodiments, this CLID field may bepopulated with “unknown caller” or the like in the event that therelationship number is a new number assigned by the SLS platform 115 andnot yet recognized by the SLS phone app (more details regarding such anembodiment is described below relative to FIGS. 4 and 5 ). Notably, itis envisioned that other embodiments may populate this CLID field, orprovide other metadata, that serves to trigger recognition of theincoming call as a call directed to the SLS phone number of the SLSsubscriber. As such, by describing the exemplary embodiment to populatethis CLID field with a combination of the relationship number and thethird party's actual phone number, the scope of the disclosure will notbe limited.

Having recognized that the incoming call is from the SLS platform 115,the SLS module 105 stores the combination of the relationship number1.678.222.0001 and the phone number being used by the third party1.305.229.9999 in the local SLS database 106. To complete the exemplarycall, the SLS module 105 may cause the actual phone number associatedwith the third party TD 120, 1.305.229.9999, to be rendered on displaycomponent 103 as an identification of the calling party and rings thephone. Once the Subscriber #1 answers, the SLS platform 115 connects thetwo legs of the SLS (leg 1 represented by third party TD 120A to SLSplatform 115 and leg 2 represented by SLS platform 115 to subscriber TD110) by methods known and understood by those of ordinary skill in theart of telecommunications. As non-limiting examples, the calls can beconnected via a forward or a bridge, as well as other technologies knownto those with ordinary skill in the art. Notably, it is envision by thisdisclosure that the call could be routed through the intermediate SLSplatform 115 as a way of enabling the SLS between the third party TD 120and the subscriber TD 110.

Notably, in the example, the combination of the relationship number1.678.222.0001 and the phone number being used by the third party1.305.229.9999 is now stored in the central SLS database 116 at SLSplatform 115 and also in the local SLS database 106 in subscriber TD110. As one of ordinary skill in the art will recognize, the importanceof the relationship number is that it may also provide a mechanism bywhich the SLS platform 115 may intercept SLS calls originating fromsubscriber TD 110 (in much the same way as the SLS phone number providesa mechanism by which the SLS platform may intercept SLS callsoriginating from the third party TD 120).

With regard to the second illustrative embodiment, suppose Subscriber #1desires to initiate a call to the third party associated with1.305.229.9999 from its SLS phone number 1.770.555.0001. Because thethird party associated with 1.305.229.9999 had previously placed a callto the SLS phone number 1.770.555.0001, the relationship combinationthat maps Subscriber #1's SLS phone number 1.770.555.0001 and the thirdparty phone number 1.305.229.9999 to relationship number 1.678.222.0001is already stored in both the central SLS database 116 at SLS Platform115 and the local SLS database 106 in subscriber TD 110.

To place calls from its SLS phone number, Subscriber #1 uses the SLSphone app of SLS module 105 as his dialer, as a non-limiting example ofone potential embodiment. In the SLS dialer (not depicted in the FIGS.),Subscriber #1 dials the third party phone number 1.305.229.9999, whichis reflected in the Private Relationship ID Tables 310 and 315 as beingassociated with his Contact #1. The SLS module 105 queries SubscriberRelationship ID Table 315 in local SLS database 106 and translates thedialed third party number 1.305.229.9999 to relationship number1.678.222.0001. The SLS module 105 may indicate to the SLS subscribervia display 103 that it is calling 1.305.229.9999, but instead it callsthe relationship number 1.678.222.0001. By calling the relationshipnumber associated with Contact #1, the communications network 125 routesthe call to the SLS platform 115 instead of directly to third party TD120.

When the SLS platform 115 processes this first leg of the SLS, it mayrecognize that the calling number is the SLS subscriber's primary number1.408.544.1212 (which is associated with the subscriber's SLS phonenumber 1.770.555.0001) and the called number is the relationship number1.678.222.0001. Querying the Subscriber Relationship ID Table 310 incentral SLS database 116, the redirection module 117 may apply thefollowing logic: “when primary number 1.408.544.1212 calls relationshipnumber 1.678.222.0001, it is actually SLS phone number 770.555.0001calling 1.305.229.9999.” The SLS platform 115 may then follow that logicand complete the second leg of the SLS by calling the actual number1.305.229.9999 associated with third party TD 120 using the SLS number1.770.555.0001.

Notably, in completing the second leg of the SLS and connecting the twolegs (in much the same way as described above for SLS calls originatingfrom a third party), the SLS platform 115 may modify the CLID fielddisplayed for the benefit of TD 120 to be something other than the SLSphone number 1.770.555.0001 from which the second leg of the SLS ismade. As a non-limiting example, it is envisioned that the SLS platform115 may modify the CLID field to be the primary number of subscriber TD110.

As described above, it is envisioned that another SLS subscriber (forexample, Subscriber #2 having SLS phone number 1.770.555.0002) couldalso initiate the first leg of an SLS call by using the relationshipnumber 1.678.222.0001. In this situation, the SLS platform 115 woulddirect the second leg of the SLS to a different third party numberassociated with a contact of Subscriber #2. As is described above, theencoded third party phone number called by the SLS platform 115 for thesecond leg of the call is derived from the combination of the SLS phonenumber and the relationship number.

With regard to the third embodiment (the third embodiment describes thesecond embodiment when the call signal of the first leg does not includethe CLID or any other data useful for identification of the phone numberbeing used by and associated with the calling TD), suppose Subscriber #1desires to initiate a call to the third party associated with1.305.229.9999, third party TD 120A, from its SLS phone number1.770.555.0001. Notably, although the primary phone number1.305.229.9999 associated with third party TD 120 is described herein asa primary phone number, it will be understood that it may, in fact, be asecond line number in embodiments where the third party is also an SLSsubscriber.

Returning to FIGS. 3A-3B and the third illustrative embodiment,Subscriber #1 places a call to the third party's primary phone number1.305.229.9999. To place calls from its SLS phone number, Subscriber #1uses the SLS phone app of SLS module 105 as his dialer, as anon-limiting example of one potential embodiment. In the SLS dialer (notdepicted in the FIGS.), Subscriber #1 dials the third party phone number1.305.229.9999, which is reflected in the Private Relationship ID Tables310 and 315 as being associated with his Contact #1. The SLS module 105queries Subscriber Relationship ID Table 315 in local SLS database 106using the following logic: subscriber TD 110 wants to place a callthrough its SLS to 1.305.229.9999; because 1.305.229.9999 had previouslyplaced a call to the SLS phone number 1.770.555.0001, the relationshipcombination maps Subscriber #1's SLS phone number 1.770.555.0001 and thethird party phone number 1.305.229.9999 to relationship number1.678.222.0001.

Having queried the relationship number, the SLS module 105 places thefirst leg of the SLS from subscriber's primary phone number1.408.544.1212 to relationship number 1.678.222.0001. Notably, it isenvisioned that SLS module 105 can place the first leg using protocolsand standards such as, but not limited to SIP, CAMEL or CAP, ROSE, VOIP,etc. Moreover, it is envisioned that SLS module 105 can places the firstleg from any telephone number associated with the TD that can make callsthrough communications network 125. The SLS module 105 may indicate tothe SLS subscriber via display 103 that it is calling 1.305.229.9999,but instead it calls the relationship number 1.678.222.0001. By callingthe relationship number associated with Contact #1, the communicationsnetwork 125 routes the call to the SLS platform 115 instead of directlyto third party TD 120.

As described above, it is envisioned that another SLS subscriber (forexample, Subscriber #2 having SLS phone number 1.770.555.0002) couldalso initiate the first leg of an SLS call by using the relationshipnumber 1.678.222.0001. In this situation, the SLS platform 115 woulddirect the second leg of the SLS to a different third party numberassociated with a contact of Subscriber #2.

Returning to FIGS. 3A-3B and the third illustrative embodiment, the SLSplatform 115 accepts the first leg of the SLS. When the SLS platform 115processes this first leg it does not recognize that the calling numberis the SLS subscriber's primary number 1.408.544.1212 (which isassociated with the subscriber's SLS phone number 1.770.555.0001)because communications network 125 does not make the CLID, or any otherdata useful for identification of the phone number being used by andassociated with Subscriber #1's TD for the call, available, reliablyavailable, or consistently available, etc.

When querying the Subscriber Relationship ID Table 310 in central SLSdatabase 116, the redirection module 117 computes the following result:“because there is no calling party telephone number to query asassociated with relationship number 1.678.222.0001, the redirectionmodule 117 cannot determine which SLS phone number is calling and towhich third party telephone number the second leg of the SLS should bedirected.” Consequently, the SLS platform 115 cannot complete the secondleg of the SLS by calling 1.305.229.9999 using the SLS number1.770.555.0001 even though the relationship number 1.678.222.0001 hadbeen previously associated with Subscriber #1 and the calling thirdparty and stored in Subscriber Relationship ID Table 310 in central SLSdatabase 116.

To deal with these circumstances and ensure that the second leg of theSLS is completed, SLS platform 115 is capable of leveraging a third setof intermediate phone numbers, specifically the phone numbers related tothe Subscriber Special Relationship ID Tables in FIG. 3C-3D. For certainthird parties, to which the SLS subscriber wishes to direct an SLS call,a Subscriber Special Relationship ID Table 320 may be maintained on thecentral SLS database 116 of SLS platform 115. Like the relationshipnumbers of Subscriber Relationship ID Table 310, the SLS provider hasanother list of dialable phone numbers, i.e., special relationshipnumbers, which are maintained. These special relationship numbers mayalso be “hidden numbers” that are used to make the first leg of the callbetween the subscriber TD 110 and the SLS platform 115 whencommunications network 125 does not make the CLID, or any other datauseful for identification of the phone number being used by andassociated with subscriber TD 110 for the call, available, reliablyavailable, or consistently available, etc.

In some embodiments, the SLS provider may be the owner, lessee, orassignee, etc. of these special relationship numbers. Like the SLS phonenumbers and the relationship numbers, one of ordinary skill in the artwill recognize that, depending on which provider network therelationship numbers are associated, a call directed at/directed fromthe relationship numbers are usually also routed through theirassociated provider network. For example, in FIG. 2 , if the specialrelationship numbers are associated with first provider network201/second provider network 202, then any call directed at/directed fromthe special relationship numbers is routed through first providernetwork 201/second provider network 202 regardless of the relationshipnumber being owned, lease, or assigned, etc. by an SLS provider.

Concerning the Special Subscriber Relationship ID Table 320, one ofordinary skill in the art will understand that certain embodiments maynot formally distinguish one SLS subscriber's records from that ofanother via individual subscriber special relationship ID tables.Rather, as is understood in the art of database management and query, amore general relational database including records associated withmultiple SLS subscribers may be used to map SLS subscriber number andthird party number combinations to given special relationship numbers.As such, it will be understood by one of ordinary skill in the art thatthe description in this disclosure of exemplary embodiments that includeindividual subscriber special relationship ID tables are offered forillustrative purposes only and will not limit the scope of thedisclosure.

Additionally, concerning the use of special relationship numbers, it isenvisioned that, unlike the relationship numbers, special relationshipnumbers may only be used for a specific SLS phone number and third partynumber combination, i.e., in certain embodiments a given specialrelationship number is unique to a given subscriber phone number andthird party phone number combination. For example, in an illustrativeembodiment, if there are four SLS subscribers, D, E, F and J, only D'sdatabase records may map special relationship number X to third partynumber J. Notably, in this exemplary scenario, the subscriber phonenumber and third party number combination DJ is meant to envision a casewhere D has a special calling relationship with J. In such case,although J is a subscriber to the SLS it may also be treated as a thirdparty caller relative to SLS subscriber D. To carry the example further,if D has a special relationship with J, it is not the case that J alsohas a special relationship with D. Additionally, it is envisioned thatin certain embodiments a special relationship number may be used forpurposes other than to map a third party calling number in SubscriberSpecial Relationship ID Table 320. For example, a given specialrelationship number may be used by the SLS platform 115 for multiplepurposes, with the specific meaning established as part of theclient-server negotiation.

Like the SLS phone numbers and the relationship numbers, the SLSprovider essentially has a group of special relationship numbers ininventory, and the SLS provider assigns the special relationship numbersas described above, and as described in greater detail below. Regardingthe SLS provider's inventory of special relationship numbers, one ofordinary skill in the art will recognize that the special relationshipnumbers may be random and generally unrelated to each other, i.e.,although the exemplary relationship numbers depicted in the FIG. 3C-3DSubscriber Special Relationship ID Tables are sequential, it isenvisioned that such is not the case in all embodiments.

Moreover, one of ordinary skill in the art will recognize that, althoughthe exemplary special relationship numbers depicted in the FIG. 3C-3DSubscriber Special Relationship ID Tables include a specific countrycode, area code, and seven digit directory number, it is envisioned thatany country code, area code and directory number system known to thoseskilled in the art is included within the scope of this disclosure.Additionally, it is envisioned that the SLS provider can maintain alarge and diverse inventory of special relationship numbers; each beingassociated with its respective provider network and, consequently, eachrouting through its associated provider network when leveraged by theSLS.

Referring again to FIGS. 3C-3D and the Subscriber Special RelationshipID Tables, the example third parties with numbers 1.305.229.9999,1.212.777.8888 and 1.408.333.2222 have been issued special relationshipnumbers 1.678.333.0001, 1.678.333.0002 and 1.678.333.0003. Other thirdparties in different situations and with different circumstances arewithin the scope of this disclosure. For example, it is envisioned bythis disclosure that the special relationship numbers could have beenpreviously assigned and stored in the necessary databases or, the numbercould have be assigned on the fly when an subscriber TD attempts toplace a call to a third party from and SLS number but the CLID of thecalling TD is not available.

As mentioned above, the special relationship numbers may be “behind thescenes” numbers that are hidden from the SLS subscriber and any thirdparty receiving a call from the SLS subscriber through the SLS. In thisthird illustrative embodiment, SLS platform 115 has effectivelyintercepted the first leg of the SLS but is unable to determine that thecall was intended for third party TD 120 (this was described above). Aswill be described in greater detail below, SLS platform 115 may take anaction that involves the special relationship number such that the callcan be terminated at third party TD 120. Essentially, by leveraging thespecial relationship number, an SLS provider may insert itself into themiddle of a call between a third party TD 120 and a subscriber TD 110even though communications network 125 does not make the CLID, or anyother data useful for identification of the phone number being used byand associated with subscriber TD 110 for the first leg, available,reliably available, or consistently available, etc.

More specifically, when the SLS platform 115 receives a call to aspecific special relationship number, the SLS platform 115 does not needthe CLID, or any other data useful for identification of the phonenumber being used by and associated with subscriber TD 110 for the firstleg. Instead, the SLS platform 115 has assigned the specific specialrelationship number to that particular SLS subscriber and, furthermore,it can determine the third party to which the second leg is theintended. It therefore has all of the necessary information to completethe second leg of the call.

Returning to the third illustrative embodiment, because the SLS platform115 cannot complete the second leg of the SLS, the SLS platform 115 maycommunicate to the SLS module 105 on subscriber TD 110 that a queryerror has occurred. It is known to those with ordinary skill in the artthat methods for communicating this query error may include the use ofprotocols and standards such as, but not limited to, SS7 protocol suite,SIP, CAMEL or CAP, ROSE, VOIP, etc. Notably, it is envisioned by thisdisclosure that the SLS platform 115 may also communicate to the SLSphone app running on SLS module 105 the special relationship numberassigned or to be assigned to the third party phone number.

Additionally, it is envisioned by this disclosure that the SLS platform115 may assign a special relationship number to the third party phonenumber upon the occurrence of a query error (such as occurred in thethird illustrative embodiment), upon a specific request by the SLSsubscriber (either directly to the SLS provider, indirectly to the SLSprovider using the SLS application, etc.), upon a specific triggeringevent, e.g., the roaming of the subscriber TD 110 to a foreigncommunications network, etc. One of ordinary skill in the art willrecognize that the SLS provider, the SLS platform 115, etc. candetermine the location of an SLS subscriber through a variety oftechniques. Non-limiting examples of these techniques include GPSlocation service on the TD, access to the geographic information of thenetwork, direct communication with the SLS subscriber as to theirimmediate location, triangulation based on tower identifiers, etc.

Finally, it is envisioned by this disclosure that the duration of theassignment of the special relationship number to a third party phonenumber may depend on a variety of factors. As non-limiting examples, theduration of the assignment may be only until a specific event occurs(e.g. a single call or a set number of calls are placed to the specialrelationship number), based on a timer, or durable until explicitlycancelled by the SLS subscriber either directly or indirectly.

Returning to the third illustrative embodiment, regardless of how, whenor for how long the special relationship number is assigned, the SLSmodule 105 may eventually receive a communication from the SLS platformwith the special relationship number assignment information and itstores the combination of the special relationship number 1.678.333.0001and the phone number being used by the third party 1.305.229.9999 in thelocal SLS database 106 in Subscriber Special Relationship ID Table 325.Notably, in the example, the combination of the special relationshipnumber 1.678.333.0001 and the phone number being used by the third party1.305.229.9999 is now stored in the central SLS database 116 at SLSplatform 115 and also in the local SLS database 106 in subscriber TD110. As one of ordinary skill in the art will recognize, the importanceof the special relationship number is that it provides a mechanism bywhich the SLS platform 115 may intercept SLS calls originating fromsubscriber TD 110 and complete the second leg of the call to the thirdparty TD 120 even when communications network 125 does not make theCLID, or any other data useful for identification of the phone numberbeing used by and associated with subscriber TD 110 for the call,available, reliably available, or consistently available, etc.

Returning to the third illustrative embodiment, despite SLS platform115's query error, SLS module 105 can reestablish the first leg of theSLS using the special relationship number associated with the thirdparty. The SLS module 105 queries Subscriber Relationship ID Table 325in local SLS database 106 and translates the intended third party number1.305.229.9999, which is reflected in the Private Special RelationshipID Tables 320 and 325 as being associated with his Contact #1, tospecial relationship number 1.678.333.0001. Having queried the specialrelationship number, the SLS module 105 places the first leg of the SLSfrom subscriber's primary phone number 1.408.544.1212 to specialrelationship number 1.678.333.0001. Notably, it is envisioned that SLSmodule 105 can place the first leg using protocols and standards suchas, but not limited to SIP, CAMEL or CAP, ROSE, VOIP, etc. Moreover, itis envisioned that SLS module 105 can place the first leg from anytelephone number associated with the TD that can make calls throughcommunications network 125. The SLS module 105 may indicate to the SLSsubscriber via display 103 that it is calling 1.305.229.9999, butinstead it calls the special relationship number 1.678.333.0001. Bycalling the special relationship number associated with Contact #1, thecommunications network 125 routes the call to the SLS platform 115instead of directly to third party TD 120.

When the SLS platform 115 processes this first leg of the SLS at thespecial relationship number, it recognizes that the calling party is theSLS subscriber. As a result, the SLS platform 115 does not need to querythe Subscriber Relationship ID Table 310 in central SLS database 116.Instead, the SLS platform 115 queries Subscriber Special Relationship IDTable 320 using the following logic: “a call was received to specialrelationship number 1.678.333.0001, so this means that primary number1.408.544.1212 is wanting to call 1.305.229.9999 using its SLS phonenumber 770.555.0001.” The SLS platform 115 may then follow that logicand complete the second leg of the SLS by calling the actual number1.305.229.9999 associated with third party TD 120 using the SLS number1.770.555.0001.

Notably, in completing the second leg of the SLS and connecting the twolegs, the SLS platform 115 may modify the CLID field displayed for thebenefit of TD 120 to be something other than the SLS phone number1.770.555.0001 from which the second leg of the SLS is made. As anon-limiting example, it is envisioned that the SLS platform 115 maymodify the CLID field to be the primary number of subscriber TD 110. Oneof ordinary skill in the art would understand that, unlike therelationship numbers, another SLS subscriber (for example, Subscriber #2having SLS phone number 1.770.555.0002) could not initiate the first legof an SLS call by using the special relationship number 1.678.333.0001when the special relationship number is assigned to Subscriber #1. Tocomplete the exemplary call, the SLS platform 115 connects the two legsof the SLS (leg 1 represented by subscriber TD 110 to SLS platform 115and leg 2 represented by SLS platform 115 to third party TD 120A) bymethods known and understood by those of ordinary skill in the art oftelecommunications. As non-limiting examples, the calls can be connectedvia a forward or a bridge, as well as other technologies known to thosewith ordinary skill in the art. Notably, it is envision by thisdisclosure that the call could be routed through the intermediate SLSplatform 115 as a way of enabling the SLS between the third party TD 120and the subscriber TD 110. It should also be appreciated that ratherthan establishing a call, such as a circuit switched call or a packetswitched call, the process may simply result in establishing a virtualdata connection for the delivery of an SMS, MIMS or text message or thelike.

FIGS. 4A-4E collectively illustrate an exemplary method 400 forimplementing an SLS call between a third party TD, such as third partyTD 120 and a TD associated with an SLS subscriber, such as subscriber TD110 when the call signal from the subscriber TD 110 does not include theCLID or any other data useful for identification of the phone numberbeing used by and associated with subscriber TD 110 for the call.Accordingly, for the SLS embodiment of method 400 it is envisioned thatthe SLS platform 115 may be positioned to experience a query error whenprocessing the first leg of the SLS because it is missing theinformation necessary to determine to which phone number the second legof the SLS should be directed.

At block 402, a call is directed to and received by an SLS platform 115.Notably, the call is envisioned to be any communication overcommunications network 125 that is directed to SLS platform 115,regardless of whether such communication originates from a subscriber TD110 or a third party TD 120. One of ordinary skill in the art willrecognize that a communication may include the use of protocols andstandards such as, but not limited to, SS7 protocol suite, SIP, CAMEL orCAP, ROSE, VOIP, etc.

Next, at decision block 404, the SLS platform 115 determines whether thecall originated from a third party TD 120 directed to an SLS subscriber,i.e., whether a third party has dialed an SLS phone number associatedwith an active SLS subscriber. If the communication was not a call thatoriginated from a third party TD 120, then the “no” branch is followedto block 432 of FIG. 4C. If the call did, in fact, originate from athird party TD 120, then the “yes” branch is followed to block 406.Notably, if a call is directed to the SLS platform 115, one of ordinaryskill in the art will recognize that the communication was either a callto an SLS phone number (if dialed by a third party TD 120), a call to arelationship number (if originating from an SLS client of a subscriberTD 110), or a data communication originating from an SLS client of asubscriber TD 110 (not depicted in the figures).

At block 406, the SLS platform 115 queries central SLS database 116 forthe phone number being used by third party TD 120 in association withthe SLS phone number that caused the call to be routed to the SLSplatform 115. If at decision block 408, the SLS platform 115successfully queries the phone number being used by third party TD 120and SLS phone number combination, then the “yes” branch is followed toblock 422 of FIG. 4B. If the phone number being used by third party TD120 and SLS phone number combination are not successfully queried, thenthe “no” branch is followed to block 410.

At block 410, the SLS platform 115 may associate a new relationshipnumber with the phone number being used by third party TD 120 to makethe call, the SLS subscriber's primary phone number and the subscriber'sSLS phone number. At block 412, the central SLS database 116 is updatedto include the newly created record—the phone number being used by thirdparty TD 120 to make the call is listed as a contact of the SLSsubscriber in the Subscriber Relationship ID Table 310. At block 414, acall is established between the SLS platform 115 and the subscriber TD110. In some non-limiting embodiments of block 414, the SLS platform 115initiates the call through the communication network 125's voice channelwith the subscriber TD 110 by dialing its primary phone number from therelationship number of block 410. In other non-limiting embodiments ofblock 414, the subscriber's TD 110 initiates the call through thecommunication network 125's voice channel with the SLS platform 115 bydialing the relationship number of block 410 from the subscriber TD110's primary phone number after receiving a data communication from theSLS platform 115 with information containing the relationship number ofblock 410 and instructions to initiate the call (again, one of ordinaryskill in the art will recognize that a communication may include the useof protocols and standards such as, but not limited to, SS7 protocolsuite, SIP, CAMEL or CAP, ROSE, VOIP, etc). In certain non-limitingembodiments of block 414, the SLS platform 115 may populate the CLIDfield of the call between it and the subscribers TD 110 with acombination of the newly assigned relationship number and the phonenumber being used by third party TD 120 to make the call.

At block 416, the local SLS database 106 updates to include the newlyassigned relationship number in association with the phone number beingused by third party TD 120 to make the call. At block 418, the phonenumber being used by third party TD 120 to make the call is displayed tothe SLS subscriber and the SLS subscriber is alerted to the incomingcall. Notably, it is envisioned that displaying the phone number beingused by third party TD 120 to make the call may include rendering theCLID field itself, rendering a picture of the third party, rendering aname, etc. as is understood by those with ordinary skill in the art ofgraphical user displays and interfaces. At block 420, the call fromblock 402 is bridged with the call from block 414 resulting in an activecall between third party TD 120 and subscriber TD 110. One of ordinaryskill in the art will recognize that there are many systems and methodsknown and understood for bridging or connecting a plurality of separatecalls (the legs of the SLS); consequently, this disclosure is notlimited by the used example “bridged.”

It is envisioned that the steps taken at block 418 of the method 400 maydiffer in some embodiments. For instance, when a third party TD 120'scall to an SLS phone number is received at the SLS platform 115, and thephone number being used by third party TD 120 to make the call is notyet associated with a relationship number, the SLS platform 115 mayassign a next relationship number as described relative to blocks410-412 then establish a call with the subscriber TD 110 as described in414. The SLS module 105 of the subscriber TD 110, having no record ofthe new relationship number in its local database 106, may display thecalling number as “unknown caller” on the display of the subscriber TD110. At the same time, the SLS module 105 may establish a dataconnection over communications network 125 with the SLS platform 115 forthe purpose of acquiring the third party calling number associated withthe new relationship number. Once the phone number being used by thirdparty TD 120 to make the call is acquired, the SLS module 105 may updatethe local database 106 and change the display from “unknown caller” tothe phone number being used by third party TD 120 to make the call.

Turning now to FIG. 4B, if the “yes” branch is followed from decisionblock 408 of FIG. 4A, at block 422 the SLS platform 115 queries thecentral SLS database 116 for the relationship number that maps to thecombination of the phone number being used by third party TD 120 andsubscriber's SLS phone number. At block 423, the SLS platform 115determines if it should modify the relationship number of block 422based on the location of the subscriber TD 110. If at decision block 423the SLS platform 115 determines that it should modify the relationshipnumber of block 422, then the “yes” branch is followed to block 410 ofFIG. 4A. If at decision block 423 the SLS platform 115 determines thatit should not modify the relationship number of block 422, then the “no”branch is followed to block 424.

At block 424, a call is established between the SLS platform 115 and thesubscriber TD 110. In some non-limiting embodiments of block 424, theSLS platform 115 initiates the call through the communication network125's voice channel with the subscriber TD 110 by dialing its primaryphone number from the relationship number of block 422. In othernon-limiting embodiments of block 414, the subscriber's TD 110 initiatesthe call through the communication network 125's voice channel with theSLS platform 115 by dialing the relationship number of block 422 fromthe subscriber TD 110's primary phone number after receiving a datacommunication from the SLS platform 115 with information containing therelationship number of block 422 and instructions to initiate the call.In certain non-limiting embodiments of block 414, the SLS platform 115may populate the CLID field of the call between it and the subscribersTD 110 with a combination of the assigned relationship number and thephone number being used by third party TD 120 to make the call.

It is envisioned that in some embodiments of block 424 an SLS module 105may recognize that an incoming call is from the SLS platform 115 byvirtue of the call originating from a relationship number. At block 426,the phone number being used by third party TD 120 to make the call isdisplayed to the SLS subscriber and the SLS subscriber is alerted to theincoming call. Notably, it is envisioned that displaying the phonenumber being used by third party TD 120 to make the call may includerendering the CLID itself, rendering a picture of the third party,rendering a name, etc. as is understood by those with ordinary skill inthe art of graphical user displays and interfaces. In certainnon-limiting embodiments of block 426, the information populated by theSLS platform 115 in the CLID field of the call between SLS platform 115and the subscribers TD 110 may cause the SLS module 105 to handle thecall and display the associated third party CLID for the benefit of thesubscriber.

At block 430, the call from block 402 is bridged with the call fromblock 424 resulting in an active call between third party TD 120 andsubscriber TD 110. One of ordinary skill in the art will recognize thatthere are many systems and methods known and understood for bridging orconnecting a plurality of separate calls (the legs of the SLS);consequently, this disclosure is not limited by the used example“bridged.” It is envisioned that, if the subscriber elects not to answera call to the SLS phone number, the SLS module 105 in some non-limitingembodiments may use a voicemail service or message service in responseto the unanswered call. That is, it is envisioned that an SLS servicemay provide features and services dedicated to the SLS subscriber andseparate from similar features and services associated with thesubscriber's primary number.

Turning now to FIG. 4C, if the “no” branch is followed from block 404 ofFIG. 4A, at decision block 432 the SLS platform 115 determines if thecall was directed to a relationship number of any kind (relationshipnumber or special relationship number). Notably, if the call is directedto a relationship number of any kind, then it must have originated froma subscriber TD 110. If the call was not directed to a relationshipnumber of any kind, the “no” branch is followed to block 442 of FIG. 4E.If, however, the call was routed to the SLS platform 115 because it wasdirected to a relationship number of any kind then the “yes” branch isfollowed to block 433.

At block 433, the SLS platform 115 determines if the call was directedto a relationship number (as distinct from a special relationshipnumber). If the call was not directed to a relationship number, the “no”branch is followed to block 452 of FIG. 4D. If, however, the call wasrouted to the SLS platform 115 because it was directed to a relationshipnumber then the “yes” branch is followed to block 434.

At block 434, the SLS platform 115 attempts to obtain the phone numberbeing used by subscriber TD 110 to call the relationship number. If atdecision block 435, the SLS platform 115 is unable to obtain the phonenumber being used by subscriber TD 110 because the call signal from thesubscriber TD 110 does not include the CLID or any other data useful foridentification of the phone number being used by and associated withsubscriber TD 110 for the call to the relationship number, then the “no”branch is followed to block 452 of FIG. 4D. If the SLS platform 115 isable to successfully obtain the phone number being used by subscriber TD110 to call the relationship number, then the “yes” branch is followedto block 436.

At block 436, the central SLS database 116 is queried for the thirdparty TD 120's phone number in combination with the relationship numberthat was dialed by subscriber TD 110 that resulted in the call routingto the SLS platform 115, the SLS phone number and the phone number beingused by subscriber TD 110 to call the relationship number. At block 437,the SLS platform 115 determines the third party TD 120's phone numberwith which the relationship number and the phone number being used bysubscriber TD 110 to call the relationship number is associated. Atblock 438, a call is established between the SLS platform 115 and thethird party TD 120. In some non-limiting embodiments of block 438, theSLS platform 115 initiates the call through the communication network125's voice channel with the third party TD 120 by dialing the thirdparty TD 120's phone number determined in block 436. In anothernon-limiting embodiments of block 438, the SLS platform 115 initiatesthe call through the communication network 125's data channel with thethird party TD 120 by dialing the third party TD 120's phone numberdetermined in block 436. In some non-limiting embodiments of block 438,the SLS platform 115 may populate the CLID field of the call between itand the third party TD 120 with the SLS phone number of subscriber TD110. In other non-limiting embodiments of block 438, the SLS platform115 may populate the CLID field of the call between it and the thirdparty TD 120 with the primary phone number of subscriber TD 110.

At block 440, the call from block 402 is bridged with the call fromblock 438 resulting in an active call between subscriber TD 110 andthird party TD 120. One of ordinary skill in the art will recognize thatthere are many systems and methods known and understood for bridging orconnecting a plurality of separate calls (the legs of the SLS);consequently, this disclosure is not limited by the used example“bridged.” It is envisioned that, if the third party elects not toanswer a call to it from SLS, the SLS platform 115 in some non-limitingembodiments may continue the bridge even when the call from block 438 isrouted to its voicemail service or message service.

Turning now to FIG. 4D, if the “no” branch is followed from block 433 ofFIG. 4C, at decision block 452 the SLS platform 115 determines if thecall was directed to a special relationship number (as distinct from arelationship number). If the call was not directed to a specialrelationship number, then the “no” branch is followed to block 442 ofFIG. 4E. If, however, the call was directed to a special relationshipnumber, then the “yes” branch is followed to block 454.

At block 454, the central SLS database 116 is queried for the thirdparty TD 120's phone number in combination with the special relationshipnumber that was dialed by subscriber TD 110 that resulted in the callrouting to the SLS platform 115. At block 456, the SLS platform 115determines the third party TD 120's phone number with which the specialrelationship number is associated. At block 458, a call is establishedbetween the SLS platform 115 and the third party TD 120. In somenon-limiting embodiments of block 458, the SLS platform 115 initiatesthe call through the communication network 125's voice channel with thethird party TD 120 by dialing the third party TD 120's phone numberdetermined in block 456. In other non-limiting embodiments of block 458,the SLS platform 115 initiates the call through the communicationnetwork 125's data channel with the third party TD 120 by dialing thethird party TD 120's phone number determined in block 456. In somenon-limiting embodiments of block 458, the SLS platform 115 may populatethe CLID field of the call between it and the third party TD 120 withthe SLS phone number of subscriber TD 110. In other non-limitingembodiments of block 458, the SLS platform 115 may populate the CLIDfield of the call between it and the third party TD 120 with the primaryphone number of subscriber TD 110.

At block 460, the call from block 402 is bridged with the call fromblock 458 resulting in an active call between subscriber TD 110 andthird party TD 120. One of ordinary skill in the art will recognize thatthere are many systems and methods known and understood for bridging orconnecting a plurality of separate calls (the legs of the SLS);consequently, this disclosure is not limited by the used example“bridged.” It is envisioned that, if the third party elects not toanswer a call to it from SLS, the SLS platform 115 in some non-limitingembodiments may continue the bridge even when the call from block 458 isrouted to its voicemail service or message service.

Turning now to FIG. 4E, if the “no” branch is followed from block 432 ofFIG. 4C or block 452 of FIG. 4D, at decision block 442 the SLS platform115 determines that the communication is a data communication overcommunications network 125 that originated from an SLS client of asubscriber TD 110. If not, then it is assumed that it was an errantcommunication and the “no” branch is followed to block 444 and thecommunication is disconnected. If the communication did originate from aSLS client, i.e., an SLS module 105 in a subscriber TD 110 associatedwith a subscriber to the SLS service, then the “yes” branch is followedto block 446. It is envisioned that the communication from an SLS clientapplication to an SLS platform may be of any protocol suitable forcommunicating over communications network 125 including the use ofprotocols and standards such as, but not limited to, SS7 protocol suite,SIP, CAMEL or CAP, ROSE, VOIP, etc.

At block 446, it is deduced by the SLS platform 115 that the subscriberassociated with the calling SLS client desires to use the SLS service tocall third party TD 120's phone number with which no relationship numberof any kind has been previously associated (such as would occur at block410). The SLS module 105 has provided the request for the newrelationship number of any kind (the request specifies if it is for arelationship number or a special relationship number depending on thecircumstances), along with the third party number it desires to call, tothe SLS platform 115 via the data communication. The central SLSdatabase 116 is queried at block 446 to determine the next availablerelationship number or special relationship number for the subscriber'sgiven SLS phone number.

The SLS platform 115 may associate a new relationship number with thesubscriber's SLS phone number, the SLS subscriber's primary phone numberand the third party TD 120's phone number. The SLS platform 115 mayassociate a new special relationship number with the subscriber's SLSphone number and the third party TD 120's phone number. It is envisionedthat this associating may take into consideration whether subscriber TD110 is roaming. One of ordinary skill in the art will recognize thatthat the SLS provider, the SLS platform 115, etc. can determine thelocation of an SLS subscriber through a variety of system or methods.Non-limiting examples of these methods and system include GPS locationservice on the TD, access to the geographic information of the network,direct communication with the SLS subscriber as to their immediatelocation, etc.

It is envisioned that the SLS module 105 may communicate with the SLSplatform 115 in some embodiments to obtain a relationship number or aspecial relationship number for a third party that has not previouslybeen called via a session-based protocol such as, but not limited to, anunstructured supplementary services data (“USSD”) protocol. As isunderstood in the art of telecommunications protocols, a gateway such asa USSD gateway may be used to route messages from a signaling network toservice applications and back. In this way, certain embodiments of anSLS module 105 may communicate with an SLS platform 115 to designate andacquire a relationship number or a special relationship number to athird party who has not been called by the subscriber before via the SLS(or, for that matter, a third party who has not placed a call to thesubscriber's SLS phone number before).

Moreover, USSD is offered herein for exemplary purposes and is not meantto limit the type of communications protocol that may be used by certainembodiments. For example, it is envisioned that short message service(“SMS”) protocol, multimedia messaging service (“MMS”) protocol, and/orother protocols may be used by some embodiments. It is envisioned thatan IP-based interaction over the TD's data service may be used by someembodiments. As would be recognized by one of ordinary skill in the art,use of session based protocols or other communication protocols mayminimize temporal delays in allocating and acquiring relationshipnumbers between an SLS module 105 and an SLS platform 115. In fact, itis anticipated that any mechanism that can be used to establish acommunication path between the SLS module 105 and the SLS platform 115for the purposes of supporting the SLS can be utilized. This may includeany of the varieties of cellular data, WiFi, Bluetooth technologies,proprietary wireless or wired technologies, etc. Such channels can beused in setting up the relationship databases, sharing informationbetween the SLS module 105 and the SLS platform 115, initiating voicecommunication establishment from the TD 110 to the SLS platform 115, theTD 110 requesting the SLS platform 115 to place a call to a third partyTD 120, etc.

At block 448, the determined next available relationship number orspecial relationship number is returned to the SLS module 105 of thesubscriber TD 110. At block 450, the central SLS database 116 is updatedwith the new relationship number or the new special relationship number.The new relationship number is now associated in the central SLSdatabase 116 with the subscriber's SLS phone number, the SLSsubscriber's primary phone number and the third party TD 120's phonenumber. The new special relationship number is now associated in thecentral SLS database 116 with the subscriber's SLS phone number and thethird party TD 120's phone number. Notably, after blocks 448 and/or 450,the method 400 may return to the start of method 400 at block 402 as theSLS module 105 of the subscriber TD 110 has acquired a new relationshipnumber or new special relationship number in association with a thirdparty TD 120'S phone number. Consequently, using the newly acquiredrelationship number or special relationship number may essentially startover the method 400 with the SLS platform 115 receiving the call. If so,the method 400 would follow to FIG. 4C where the call was recognized asthe subscriber TD 110 having placed a call to the new relationshipnumber or new special relationship number.

Certain steps or blocks in the processes or process flows described inthis specification naturally precede others for the invention tofunction as described. However, the invention is not limited to theorder of the steps or blocks described if such order or sequence doesnot alter the functionality of the invention. That is, it is recognizedthat some steps or blocks may performed before, after, or parallel(substantially simultaneously with) other steps or blocks withoutdeparting from the scope and spirit of the invention. In some instances,certain steps or blocks may be omitted or not performed withoutdeparting from the invention. Also, in some instances, multiple actionsdepicted and described as unique steps or blocks in the presentdisclosure may be comprised within a single step or block. Further,words such as “thereafter”, “then”, “next”, “subsequently”, etc. are notintended to limit the order of the steps or blocks. These words aresimply used to guide the reader through the description of the exemplarymethod.

Additionally, one of ordinary skill in programming is able to writecomputer code or identify appropriate hardware and/or circuits toimplement the disclosed invention without difficulty based on the flowcharts and associated description in this specification, for example.Therefore, disclosure of a particular set of program code instructionsor detailed hardware devices is not considered necessary for an adequateunderstanding of how to make and use the invention. The inventivefunctionality of the claimed computer implemented processes is explainedin more detail in the above description and in conjunction with theFigures which may illustrate various process flows.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted as one or more instructions or code on a computer-readablemedium. Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another.

A storage media may be any available media that may be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia may comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that may be used to carry or store desired program code inthe form of instructions or data structures and that may be accessed bya computer.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (“DSL”), or wireless technologies such asinfrared, radio, and microwave, then the coaxial cable, fiber opticcable, twisted pair, DSL, or wireless technologies such as infrared,radio, acoustic and microwave are included in the definition of medium.

Disk and disc, as used herein, includes compact disc (“CD”), laser disc,optical disc, digital versatile disc (“DVD”), floppy disk and blu-raydisc where disks usually reproduce data magnetically, while discsreproduce data optically with lasers. Combinations of the above shouldalso be included within the scope of computer-readable media.

Therefore, although selected aspects have been illustrated and describedin detail, it will be understood that various substitutions andalterations may be made therein without departing from the spirit andscope of the present invention, as defined by the following claims.

What is claimed is:
 1. A method embodied within a mobile applicationoperating within a mobile communications device, wherein the mobilecommunications device includes a cellular service provider numberassociated therewith, the mobile application configured to perform theactions of: interfacing over a communications network with a second lineservice platform; receiving from the second line service platform atleast one or more additional network accessible numbers that areassigned to the mobile communications device; receiving, from the secondline service platform, and storing within a memory element of the mobilecommunications device, one or more relationship numbers that areassociated by the second line service platform with the cellular serverprovider number, wherein each of the one or more relationship numbers isstored along with a particular additional network accessible number ofthe at least one or more additional network numbers assigned to themobile communications device and a third party calling number, andwherein each of the one or more relationship numbers is a networkrecognizable number; receiving an incoming call at the mobilecommunications device, wherein the incoming call is from a particularthird party that dialed a particular relationship number that is one ofthe one or more relationship numbers and the calling line identifier ofthe incoming call is set to the particular relationship number; andusing the particular relationship number obtained from the calling lineidentifier of the incoming call, access the memory element to identify aparticular third party calling number associated with the particularthird party and the particular additional network accessible number forthe incoming call.
 2. The method of claim 1, further comprising theaction of: presenting on a display of the mobile communications device,an indication that an incoming call from the particular third party isbeing received for the particular additional network accessible number.3. The method of claim 2, further comprising the actions of: receiving acall accept actuation of a user interface of the mobile communicationsdevice; and terminating the incoming call at the mobile communicationsdevice, wherein the incoming call is established over a cellularnetwork.
 4. The method of claim 3, further comprising: receiving a callorigination actuation of a user interface of the mobile communicationsdevice, wherein the call origination actuation includes the particularrelationship number as the dialed number; initiating an outgoing callover a telecommunications network to the particular relationship numberand setting the calling line identifier of the outgoing call to thecellular service provider number, whereby the telecommunications networkwill recognize the particular relationship number as being serviced bythe second line service platform and route the outgoing call to thesecond line service platform, whereby the second line service platformwill direct the outgoing call to the particular third party callingnumber associated with the particular third party with the calling lineidentifier set to the particular additional network number associatedwith the particular relationship number and the cellular serviceprovider number.
 5. The method of claim 3, further comprising: receivinga call origination actuation of a user interface of the mobilecommunications device, wherein the call origination actuation includes asecond particular relationship number as the dialed number; initiatingan outgoing call over a telecommunications network to the secondparticular relationship number and setting the calling line identifierof the outgoing call to the cellular service provider number, wherebythe telecommunications network will recognize the second particularrelationship number as being serviced by the second line serviceplatform and route the outgoing call to the second line serviceplatform, whereby the second line service platform will direct theoutgoing call to the second particular third party calling numberassociated with a second particular third party with the calling lineidentifier set to a second particular additional network numberassociated with the second particular relationship number and thecellular service provider number.
 6. The method of claim 1, furthercomprising: receiving a call origination actuation of a user interfaceof the mobile communications device, wherein the call originationactuation includes the particular relationship number as the dialednumber; initiating an outgoing call over a telecommunications network tothe particular relationship number and setting the calling lineidentifier of the outgoing call to the cellular service provider number,whereby the telecommunications network will recognize the relationshipnumber as being serviced by the second line service platform and routethe outgoing call to the second line service platform, whereby thesecond line service platform will direct the outgoing call to theparticular third party calling number associated with the particularthird party with the calling line identifier set to the particularadditional network number associated with the particular relationshipnumber and the cellular service provider number.
 7. The method of claim1, further comprising: receiving a call origination actuation of a userinterface of the mobile communications device, wherein the callorigination actuation includes a second particular relationship numberas the dialed number; initiating an outgoing call over atelecommunications network to the second particular relationship numberand setting the calling line identifier of the outgoing call to thecellular service provider number, whereby the telecommunications networkwill recognize the second particular relationship number as beingserviced by the second line service platform and route the outgoing callto the second line service platform, whereby the second line serviceplatform will direct the outgoing call to the second particular thirdparty calling number associated with a second particular third partywith the calling line identifier set to a second particular additionalnetwork number associated with the second particular relationship numberand the cellular service provider number.
 8. A method for enabling amobile communications device to place and receive calls to one of aplurality of numbers associated with the mobile communications device,wherein the mobile communications device includes a cellular serviceprovider number associated therewith, the method comprising the actionsof: providing a mobile application accessible on a mobile applicationstore for downloading into the mobile communications device, the mobileapplication once downloaded and operating within the mobilecommunications device being configured to perform the actions of:interfacing over a communications network with a second line serviceplatform; receiving from the second line service platform at least oneor more additional network accessible numbers that are assigned to themobile communications device; receiving, from the second line serviceplatform, and storing within a memory element of the mobilecommunications device, one or more relationship numbers that areassociated by the second line service platform with the cellular serverprovider number, wherein each of the one or more relationship numbers isstored along with a particular additional network accessible number ofthe at least one or more additional network numbers assigned to themobile communications device and a third party calling number, andwherein each of the one or more relationship numbers is a networkrecognizable number; receiving an incoming call at the mobilecommunications device, wherein the incoming call is from a particularthird party that dialed a particular relationship number that is one ofthe one or more relationship numbers and the calling line identifier ofthe incoming call is set to the particular relationship number; andusing the particular relationship number obtained from the calling lineidentifier of the incoming call, access the memory element to identify aparticular third party calling number associated with the particularthird party and the particular additional network accessible number forthe incoming call.
 9. The method of claim 8, further comprising theaction of: presenting on a display of the mobile communications device,an indication that an incoming call from the particular third party isbeing received for the particular additional network accessible number.10. The method of claim 9, further comprising the actions of: receivinga call accept actuation of a user interface of the mobile communicationsdevice; and terminating the incoming call at the mobile communicationsdevice, wherein the incoming call is established over a cellularnetwork.
 11. The method of claim 10, further comprising: receiving acall origination actuation of a user interface of the mobilecommunications device, wherein the call origination actuation includesthe particular relationship number as the dialed number; initiating anoutgoing call over a telecommunications network to the particularrelationship number and setting the calling line identifier of theoutgoing call to the cellular service provider number, whereby thetelecommunications network will recognize the particular relationshipnumber as being serviced by the second line service platform and routethe outgoing call to the second line service platform, whereby thesecond line service platform will direct the outgoing call to theparticular third party calling number associated with the particularthird party with the calling line identifier set to the particularadditional network number associated with the particular relationshipnumber and the cellular service provider number.
 12. The method of claim10, further comprising: receiving a call origination actuation of a userinterface of the mobile communications device, wherein the callorigination actuation includes a second particular relationship numberas the dialed number; initiating an outgoing call over atelecommunications network to the second particular relationship numberand setting the calling line identifier of the outgoing call to thecellular service provider number, whereby the telecommunications networkwill recognize the second particular relationship number as beingserviced by the second line service platform and route the outgoing callto the second line service platform, whereby the second line serviceplatform will direct the outgoing call to the second particular thirdparty calling number associated with a second particular third partywith the calling line identifier set to a second particular additionalnetwork number associated with the second particular relationship numberand the cellular service provider number.
 13. The method of claim 8,further comprising: receiving a call origination actuation of a userinterface of the mobile communications device, wherein the callorigination actuation includes the particular relationship number as thedialed number; initiating an outgoing call over a telecommunicationsnetwork to the particular relationship number and setting the callingline identifier of the outgoing call to the cellular service providernumber, whereby the telecommunications network will recognize therelationship number as being serviced by the second line serviceplatform and route the outgoing call to the second line serviceplatform, whereby the second line service platform will direct theoutgoing call to the particular third party calling number associatedwith the particular third party with the calling line identifier set tothe particular additional network number associated with the particularrelationship number and the cellular service provider number.
 14. Themethod of claim 8, further comprising: receiving a call originationactuation of a user interface of the mobile communications device,wherein the call origination actuation includes a second particularrelationship number as the dialed number; initiating an outgoing callover a telecommunications network to the second particular relationshipnumber and setting the calling line identifier of the outgoing call tothe cellular service provider number, whereby the telecommunicationsnetwork will recognize the second particular relationship number asbeing serviced by the second line service platform and route theoutgoing call to the second line service platform, whereby the secondline service platform will direct the outgoing call to the secondparticular third party calling number associated with a secondparticular third party with the calling line identifier set to a secondparticular additional network number associated with the secondparticular relationship number and the cellular service provider number.15. A mobile application including multiple code segments operatingwithin a mobile communications device, wherein the mobile communicationsdevice includes a cellular service provider number associated therewith,the mobile application comprising: a first code segment to interface toa second line service platform, wherein the mobile application accessthe second line service platform over a communications network toreceive at least one or more additional network accessible numbers thatare assigned to the mobile communications device; a second code segmentto interface to the second line service platform to receive one or morerelationship numbers that are associated by the second line serviceplatform with the cellular server provider number, a third code segmentto store within a memory element of the mobile communications device,each of the one or more relationship numbers along with a particularadditional network accessible number of the at least one or moreadditional network numbers assigned to the mobile communications deviceand a third party calling number, and wherein each of the one or morerelationship numbers is a network recognizable number; a fourth codesegment to receive an incoming call at the mobile communications device,wherein the incoming call is from a particular third party that dialed aparticular relationship number that is one of the one or morerelationship numbers and the calling line identifier of the incomingcall is set to the particular relationship number; and a fifth codesegment to utilize the particular relationship number obtained from thecalling line identifier of the incoming call to access the memoryelement and identify a particular third party calling number associatedwith the particular third party and the particular additional networkaccessible number for the incoming call.
 16. The mobile application ofclaim 15, further comprising: a sixth code segment to present on adisplay of the mobile communications device, an indication that anincoming call from the particular third party is being received for theparticular additional network accessible number.
 17. The mobileapplication of claim 16, further comprising: a seventh code segment toreceive a call accept actuation of a user interface of the mobilecommunications device and terminate the incoming call at the mobilecommunications device, wherein the incoming call is established over acellular network.
 18. The mobile application of claim 15, furthercomprising: an eight code segment to receive a call originationactuation of a user interface of the mobile communications device,wherein the call origination actuation includes the particularrelationship number as the dialed number; a ninth code segment toinitiate an outgoing call over a telecommunications network to theparticular relationship number and setting the calling line identifierof the outgoing call to the cellular service provider number, wherebythe telecommunications network will recognize the particularrelationship number as being serviced by the second line serviceplatform and route the outgoing call to the second line serviceplatform, whereby the second line service platform will direct theoutgoing call to the particular third party calling number associatedwith the particular third party with the calling line identifier set tothe particular additional network number associated with the particularrelationship number and the cellular service provider number.
 19. Themobile application of claim 15, further comprising: a tenth code segmentto receive a call origination actuation of a user interface of themobile communications device, wherein the call origination actuationincludes a second particular relationship number as the dialed number;an eleventh code segment to initiate an outgoing call over atelecommunications network to the second particular relationship numberand setting the calling line identifier of the outgoing call to thecellular service provider number, whereby the telecommunications networkwill recognize the second particular relationship number as beingserviced by the second line service platform and route the outgoing callto the second line service platform, whereby the second line serviceplatform will direct the outgoing call to the second particular thirdparty calling number associated with a second particular third partywith the calling line identifier set to a second particular additionalnetwork number associated with the second particular relationship numberand the cellular service provider number.
 20. The mobile application ofclaim 15, wherein the mobile application is accessible for downloadingto the mobile communications device over the Internet from anapplication store.